Method and stsyem for operating and participating in fantasy leagues

ABSTRACT

A system and computer-implemented method for operating a fantasy league including: fantasy player information including performance history of one or more real-world athletes selected as fantasy players is stored. Sponsorship information associated with the fantasy player is stored on at least one of an individual or team basis. An operational request from a fantasy client device is received. An association between the operational request and the fantasy player is determined. An operational result is determined. At least one item of sponsorship information is associated with the operational result. The operational result and the sponsorship information are transmitted. An alert window is displayed at the fantasy client device including the sponsorship information.

FIELD OF THE INVENTION

The present invention generally relates to any type of fantasy league(e.g., sports fantasy leagues). The present invention specificallyrelates to operating various aspects of a fantasy league in view offacilitating sponsorship of each fantasy player on an individual basisand/or a team basis, and in view of facilitating a transmission of feedformatted content and subfeed formatted content between fantasy systems.

BACKGROUND OF THE INVENTION

A fantasy league is primarily operated by a fantasy server system basedon a particular format for facilitating player/team management by one ormore fantasy client devices in view of a statistical scoring system fordetermining a winner among members of a fantasy league supported by thefantasy client devices. For example, a football fantasy server systemwill provide access by fantasy client devices to a fantasy website forfacilitating, among other things, player drafts, player trading, waiverwires, free agent acquisitions and starting lineup selections in view ofa statistical scoring system that is based on each football player'sweekly performance as a function of the football player's position.

A fantasy league is secondarily operated by the fantasy server systembased on a particular format for providing access to fantasy playerinformation by the fantasy client devices that enhances player/teammanagement by each member of the fantasy league supported by the fantasyclient devices. For example, a football fantasy server system currentlyprovides access by fantasy client devices to a fantasy website managingfantasy player information in the form of reports, articles,commentaries, statistics and the like that is related, directly andindirectly, to past, present and future performances of football playerswhereby the information is intended to serve as a guide for player/teammanagement by each member of the fantasy football league supported bythe fantasy client devices.

Over the years since the earliest creation of fantasy server systems,efforts by designers of the fantasy server systems to realizecomprehensive sponsorship of fantasy players has been meet with limitedsuccess. The present invention significantly advances that state-of-artin sponsored fantasy server operation and fantasy client participationin fantasy leagues.

Furthermore, a transmission of fantasy player information of a fantasyplayer from a fantasy server system to a fantasy client device hashistorically involved limited types of information. The presentinvention also significantly advances the state-of-art in fantasy playerinformation of a fantasy player provided to a fantasy client device.

SUMMARY OF THE INVENTION

One form of the present invention is a fantasy league system andcomputer-implemented method for operating a fantasy league. The fantasyleague system includes a fantasy server system operable to store fantasyplayer information regarding one or more real-world athletes, storesponsorship information associated with the fantasy player on at leastone of an individual basis and a team basis, receive an operationalrequest from the fantasy client device, said operational requestdesignating an operational aspect, determine an association between theoperational request and the fantasy player, determine an operationalresult based on the operational request, associate at least one item ofsponsorship information to the operational result based at least in partupon said sponsorship information associated with the fantasy player,and transmit the operational result and the at least one associated itemof sponsorship information to the first fantasy client device. Thefantasy league system also includes a fantasy client device operable tosend an operational request, and display an alert window including thesponsorship information based on the transmitted operational result.

A second form of the present invention is a fantasy league system andcomputer-implemented method for operating a fantasy league. The fantasyleague system includes a fantasy server system operable to store fantasyplayer information regarding one or more real-world athletes, storesponsorship information associated with the fantasy player on at leastone of an individual basis and a team basis, receive a fantasy playerdraft request from the first fantasy client device specifying thefantasy player, determines a draft selection based on the fantasy playerdraft request, associates the fantasy player with a fantasy team basedon the determination, associate at least one item of sponsorshipinformation to the draft selection based at least in part upon saidsponsorship information associated with the fantasy player, and transmitthe draft selection and the at least one associated item of sponsorshipinformation to the first fantasy client device. The fantasy leaguesystem also includes a fantasy client device operable to send a fantasyplayer draft request, and display an alert window including thesponsorship information based on the transmitted draft selection.

The aforementioned forms and other forms as well as objects andadvantages of the present invention will become further apparent fromthe following detailed description of various embodiments of the presentinvention read in conjunction with the accompanying drawings. Thedetailed description and drawings of the various embodiments of thepresent invention are merely illustrative of the present inventionrather than limiting, the scope of the present invention being definedby the appended claims and equivalents thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary environment for practicing the presentinvention;

FIG. 2 illustrates one embodiment of fantasy player information inaccordance with the present invention;

FIG. 3 illustrates one embodiment of sponsorship information inaccordance with the present invention;

FIG. 4 illustrates a first embodiment of a flowchart representative of afantasy client request method in accordance with the present invention;

FIG. 5 illustrates a first embodiment of a web page in accordance withthe present invention;

FIG. 6 illustrates a second embodiment of a flowchart representative ofa fantasy client request method in accordance with the presentinvention;

FIG. 7 illustrates a third embodiment of a flowchart representative of afantasy client request method in accordance with the present invention;

FIG. 8 illustrates one embodiment of a flowchart representative of atransaction validation method in accordance with the present invention;

FIG. 9 illustrates a second embodiment of a web page in accordance withthe present invention;

FIG. 10 illustrates a fourth embodiment of a flowchart representative ofa fantasy client request method in accordance with the presentinvention;

FIG. 11 illustrates one embodiment of a flowchart representative of afantasy scoring method in accordance with the present invention;

FIG. 12 illustrates a third embodiment of a flowchart representative ofa fantasy substitution method in accordance with the present invention;

FIG. 13 illustrates a third embodiment of a web page in accordance withthe present invention;

FIG. 14 illustrates exemplary embodiments of fantasy client devices anda fantasy server system in accordance with the present invention;

FIG. 15 illustrates one embodiment of feed formatted content, as knownin the art;

FIG. 16 illustrates a flowchart representative of one embodiment of amethod for providing feed formatted content;

FIG. 17 illustrates a flowchart representative of one embodiment of amethod for operating a real time fantasy sports league; and

FIG. 18 illustrates a flowchart representative of one embodiment of amethod for operating a real time fantasy sports league.

DETAILED DESCRIPTION OF THE PRESENT INVENTION

FIG. 1 illustrates a network based environment employing an X number offantasy client device 20, where X≧1, a network system 30 and a fantasyserver system 40. For purposes of the present invention, the term“fantasy client device” is broadly defined herein as a device of anytype structurally configured to facilitate member participation in afantasy league of any type that is operated by a fantasy server systemof the present invention, the term “network system” is broadly definedherein as one network of any type or an interconnect array of networksof any type, and the term “fantasy server system” is broadly definedherein as one or more servers of any type structurally configured tooperate the fantasy league.

In operation, network system 30 facilitates bi-directional communicationbetween fantasy client devices 20 and fantasy server system 40 involvingaccess by fantasy client devices 20 to the fantasy league operated byfantasy server system 40. One operational aspect of the fantasy leagueas provided by fantasy server system 40 is directed to facilitatingaccess to fantasy content by fantasy client devices 20 and facilitatingfantasy game play by fantasy client devices 20 as would be appreciatedby those having ordinary skill in the art. Examples of this operationalaspect include, but are not limited to, (1) off-season actions byfantasy client devices 20 (e.g., configuring the fantasy league,accessing pre-season rankings of fantasy players and conducting a draftof the fantasy players), (2) in-season, off-time actions by fantasyclient devices 20 (e.g., managing a lineup prior to or subsequent toreal-time performances by the fantasy players, and accessing reports ofpast performances by the fantasy players and commentaries on predictedfuture performances of the fantasy players), and (3) in-season, gameplayactions by fantasy client devices 20 (e.g., managing a lineup duringreal-time performances by the fantasy players, and accessing reports ofreal-time performances and real-time playing status of the fantasyplayers).

A new and unique operational aspect of the fantasy league in accordancewith the present invention as provided by fantasy server system 40 isdirected to a realization of a comprehensive sponsorship of fantasyplayers on an individual basis and/or a team basis with an improvedexchange of fantasy content between fantasy client devices 20 andfantasy server system 40. To this end, as shown in FIG. 1, fantasyserver system 40 manages one or more records of fantasy playerinformation 50 and one or more records of sponsorship information 60,and employs a fantasy content manager 70 and fantasy gameplay manager80.

For purposes of the present invention, the term “fantasy playerinformation” is broadly defined herein as any information of any typethat is relevant, directly or indirectly, to a gameplay and performancehistory of a fantasy player as reviewed by a member of the fantasyleague (e.g., physical dimensions, statistics, injury history/status,ranking, recommendations, etc.). In one embodiment, as shown in FIG. 2,fantasy player information 50 is managed by fantasy server system 40 inthe form of fantasy player text data 51, fantasy player image data 52,fantasy player video data 53, fantasy player audio data 54, fantasyplayer multimedia data 55 and fantasy player hyperlink data 56.

For purposes of the present invention, the term “sponsorshipinformation” is broadly defined herein as any information of any typethat is relevant to an advertisement/promotion of good(s) and/orservice(s) as designated to a fantasy player on an individual basisand/or a team basis, the term “individual basis” is broadly definedherein as a designation by a sponsor of an advertisement/promotion ofgood(s) and/or service(s) to a specific player (e.g., Indianapolis Stardesignates the promotion of its paper to Peyton Manning, quarterback ofthe Indianapolis Colts), and the term “team basis” is broadly definedherein as a designation by a sponsor of an advertisement/promotion ofgood(s) and/or service(s) to a specific team (e.g., Indianapolis Stardesignates the promotion of its paper to all of the team members of theIndianapolis Colts). Similarly, in one embodiment, as shown in FIG. 2,sponsorship information 60 is managed by fantasy server system 40 in theform of sponsorship text data 61, sponsorship image data 62, sponsorshipvideo data 63, sponsorship audio data 64, sponsorship multimedia data 65and sponsorship hyperlink data 66.

In operation, fantasy content manager 70 associates relevant portions ofsponsorship information of a fantasy player to relevant portions offantasy player information of the fantasy player as needed. Inparticular, fantasy content manager 70 associates relevant portions ofsponsorship information of a fantasy player to relevant portions offantasy player information of the fantasy player in response to fantasyclient requests directed to primarily acquiring fantasy playerinformation for purposes of (1) learning/reviewing fantasy playerinformation to thereby make informed gameplay decisions concerning thefantasy player and (2) make recommendations of the fantasy player toanother member of the fantasy league. Similarly, fantasy gameplaymanager 80 associates relevant portions of sponsorship information of afantasy player to relevant portions of fantasy player information of thefantasy player in response to fantasy client requests directed toprimarily acquiring fantasy player information for purposes of (1)conducting transactions involving a fantasy player prior to and/orduring a fantasy performance period of the fantasy player (e.g.,drafting, acquiring, releasing, trading, and lineup substitutions) and(2) monitoring a scoring of the fantasy player during a fantasyperformance period of the fantasy player.

The following description of FIGS. 4-14 are directed to describingexemplary fantasy client requests scenarios to facilitate anunderstanding of the present invention by those having ordinary skill inthe art.

FIG. 4 depicts a fantasy client request in the form of a request forfantasy player information. Specifically, a stage S92 of a flowchart 90and a stage S102 of a flowchart 100 encompasses one of the fantasyclient devices 20 and fantasy content manager 70 exchanging a requestfor fantasy player information FPIRQ of one or more fantasy players(e.g., a request for player news for Peyton Manning). A stage 5104 offlowchart 100 encompasses fantasy content manager 70 determining fantasyplayer information of fantasy player(s) responsive to the informationrequest (e.g., statistics and news feed items regarding Peyton Manning).A stage S106 of flowchart 100 encompasses fantasy content manager 70associating sponsorship information of the fantasy players(s)corresponding to the fantasy player information (e.g., associating anadvertisement/promotion of Indianapolis star in text, image, audio,video, multimedia, or hyperlink form to Peyton Manning's statistics andnews feed items). Finally, a stage S94 of flowchart 90 and a stage S108of flowchart 100 encompasses the fantasy client device 20 and fantasycontent manager 70 exchanging the sponsored fantasy football playerinformation SFPI.

The present invention does not impose any limitations or anyrestrictions to the format of the sponsored fantasy player information.FIG. 5 illustrates an exemplary fantasy player news web page 110 as theform of the sponsored fantasy football player information SFPI providedto the fantasy client device 20. As shown, fantasy player statistics 111and three (3) player news feed items 112-114 are provided on webpage110. A sponsor logo feed item 115 is displayed adjacent a player newsfeed item 112 in text form. A playable sponsor video clip feed item 116is displayed adjacent player news feed item 113 in video clip form. Anda sponsor hyperlink feed item 117 is displayed adjacent players newsfeed item 114 in hyperlink form.

In view of the applications referenced in paragraph [0001] herein, thosehaving ordinary skill in the art will appreciate feed formatted contentis structured data, such as, for example Electronic Data Interchange(EDI), Extensible Markup Language (XML), or a subset of a general formatsuch as RSS (Rich Site Summary or Really Simple Syndication), a hybridor extension of some such standard, or the like. Feed formatted contentmay be accessed through a feed, stored in a local file, or the like offantasy client device 20. The aforementioned feed items are the datacorresponding to the feed formatted content of webpage 110. Concurrentlyor alternatively, subfeed formatted content in the form of a browserwindow or frame spawned by feed items can also be provided for webpage110.

In practice, the three sponsor items 115-117 can correspond to the sameor difference sponsors. Furthermore, for a subsequent request for thesame fantasy player information, new sponsorship information can beassociated with the fantasy player information. In one embodiment, thisis accomplished by implementing a technique for associating thesponsorship information of fantasy players to the fantasy playerinformation of the fantasy players based on sponsorship selectioncriteria including, but not limited to, ad-targeting based criteria,profile based criteria, event based criteria and time based criteria aswould be appreciated by those having ordinary skill in the art in viewof the applications referenced in paragraph [0001] herein.

FIG. 6 depicts a fantasy client request in the form of a recommendationof fantasy player information. Specifically, a stage S122 of a flowchart120 and a stage S132 of a flowchart 130 encompasses one of the fantasyclient devices 20 and fantasy content manager 70 exchanging arecommendation for fantasy player information FPIRC of one or morefantasy players (e.g., a recommendation for player news for PeytonManning) to be transmitted to another one of the fantasy client devices20). A stage S134 of flowchart 130 encompasses fantasy content manager70 determining fantasy player information of fantasy player(s)responsive to the information recommendation (e.g., statistics and newsfeed items regarding Peyton Manning). A stage S136 of flowchart 130encompasses fantasy content manager 70 associating sponsorshipinformation of the fantasy players(s) corresponding to the fantasyplayer information (e.g., associating an advertisement/promotion ofIndianapolis star in text, image, audio, video, multimedia, or hyperlinkform to Peyton Manning's statistics and news feed items). Finally, astage S124 of flowchart 120 and a stage S138 of flowchart 130encompasses the intended fantasy client device 20 and fantasy contentmanager 70 exchanging the sponsored recommended fantasy football playerinformation SRFPI.

A fantasy player recommendation webpage can be similarly structured tofantasy player news web page 110 as shown in FIG. 5.

FIG. 7 depicts a fantasy client request in the form of a fantasy playertransaction request. Specifically, a stage S142 of a flowchart 140 and astage S152 of a flowchart 140 encompasses a fantasy client device 20 andfantasy gameplay manager 80 exchanging a fantasy player transactionrequest TRRQ involving one or more fantasy players (e.g., a drafting, awaiver addition, a waiver release, a free agent addition, a free agentrelease and a trade involving one or more fantasy players). A stage S154of flowchart 150 encompasses fantasy gameplay manager 80 determiningwhether the fantasy player transaction request is valid or invalid.

In one embodiment, a stage S162 of a flowchart 60 encompasses fantasygameplay manager 80 determining whether the fantasy player transactionrequest is in compliance with the fantasy league transaction policy. Forexample, such a policy may specify one or more transaction time periodsand which types of transactions are legal and which types are illegalduring each transaction time period (e.g., trading can only occur fromMonday to Friday during each week of the fantasy season and a waiveraddition can only occur after three days from a fantasy player's waiverrelease). The fantasy player transaction request is denied during astage S164 of flowchart 160 if it is determined by fantasy gameplaymanager 80 not to be in compliance with the fantasy league transactionpolicy. Otherwise, fantasy gameplay manager 80 associates relevantportions of sponsorship information of the subject fantasy player(s) tothe relevant portions fantasy player information of the subject fantasyplayer(s) during a stage S166 of flowchart 160, and executes thesponsored transaction during a stage S168 of flowchart 160.

In one embodiment, an execution of the sponsored transaction invokes ageneration by fantasy gameplay manager 80 of one or more webpagesrelated to the sponsored transaction. FIG. 9 illustrates an exemplaryfantasy roster webpage 170 generated in response to a sponsoredtransaction. As shown, a fantasy team roster 171 is provided on webpage170. Provided below roster 171, a released fantasy player hyperlink 172and an associated sponsor audio clip feed item 175 are displayed. Next,an acquired fantasy player hyperlink 173 and an associated sponsormultimedia clip feed item 176 are displayed. Finally, a recommendedfantasy player hyperlink 174 and an associated sponsor text feed item177 are displayed.

Referring again to FIG. 7, a stage S144 of flowchart 140 and a stageS168 of flowchart 160 encompasses the intended fantasy client device 20and fantasy content manager 70 exchanging a fantasy player transactionconfirmation TRCM for an executed sponsored transaction, oralternatively, stage S144 of flowchart 140 and a stage S168 of aflowchart 160 encompasses the intended fantasy client device 20 andfantasy content manager 70 exchanging a fantasy player transactionrejection TRRF for an a denied transaction request.

FIG. 10 depicts a fantasy client request in the form of a fantasyplayer/team scoring request. Specifically, a stage S182 of a flowchart180 and a stage S192 of a flowchart 190 encompasses a fantasy clientdevice 20 and fantasy gameplay manager 80 exchanging a fantasy scoringrequest SCRQ involving an individual fantasy player or a team of fantasyplayers. A stage S194 of flowchart 190 encompasses fantasy gameplaymanager 80 determining a fantasy scoring of each fantasy playerresponsive to the request.

In one embodiment, a stage S202 of a flowchart 200 encompasses fantasygameplay manager 80 calculating fantasy player points in accordance witha league scoring policy based on fantasy player performance in real-timein relation to a schedule fantasy performance period. A stage S204 offlowchart 200 encompasses fantasy gameplay manager 80 determiningfantasy team scoring based on a fantasy team starting lineup and anysubstitution indicators. Stages S202 and S204 are continually updateduntil such time the scheduled fantasy performance period has ended.

For purposes of the present invention, the term “substitution indicator”is broadly defined herein as an indication of one fantasy player beingsubstituted in fantasy team lineup by another fantasy player. In oneembodiment, as shown in FIG. 12, the substitution indicator is generatedby fantasy gameplay manager 80 as a substitution time stamp during astage S212 of a flowchart 210 in response to a valid gameplay lineupsubstitution having one fantasy player designated as a substitutedfantasy player and another fantasy player designated as the replacementfantasy player. The substitution time stamp can be on based on GreenwichMean Time (“GMT”) or a time related to one or more player performanceperiods.

A stage S214 of flowchart 210 encompasses fantasy gameplay manager 80determining a substitute fantasy player's fantasy scoring and areplacement fantasy player's fantasy scoring based on the substitutiontime stamp and the player's performance periods. For example, if afantasy client device 20 transacts a replacement of Peyton Manning forTom Brady at the end of the first quarter of Manning's game as indicatedby the substitution time stamp and Brady completed his game, thenManning's scoring will be based on his only quarter of game and TomBrady's scoring will be based on the 2, 3^(rd) and 4^(th) quarters ofBrady's game. Also by example, if a fantasy client transacts areplacement of Roger Clemens for Randy Johnson at the end of the 1^(st)and 2^(nd) innings pitched by Clemens as indicated by the substitutiontime stamp and Johnson completed his game, then Clemens' scoring will bebased on his pitched 1^(st) and 2^(nd) innings and Randy Johnson'sscoring will be based on his pitched 3^(rd)-9^(th) innings. From thesetwo examples, those having ordinary skill in the art will appreciate themany benefits and various simple to complex implementations of thesubstitution time stamp in accordance with the present invention.

Referring again to FIG. 10, a stage S196 of flowchart 190 encompassesfantasy gameplay manager 80 associates relevant portions of sponsorshipinformation of the subject fantasy players(s) to the relevant portionsfantasy player information of the subject fantasy player(s) aspreviously described herein, particularly in view of sponsorshipselection criteria. A stage S184 of flowchart 180 and a stage S198 offlowchart 190 encompasses the intended fantasy client device 20 andfantasy gameplay manager 80 exchanging a fantasy player/team scoringreport SCRP.

FIG. 13 illustrates an exemplary fantasy player/team scoring report SCRPin the form of a webpage 220. As shown, five (5) fantasy players 230-234with the respective fantasy scoring 240-244 and sponsor logo feed item250-254 are displayed.

Referring to FIG. 1, the present invention does not impose anylimitations or restrictions to the structural configurations of fantasyclient devices 20, network system 30 and fantasy server system 40. FIG.14 illustrates an example implementation of the network basedenvironment illustrated in FIG. 1. Specifically, five (5) fantasy clientdevices in the form of a personal computer 21, a laptop 22, a personaldata assistant 23, a mobile phone 24 and a smart phone 25 arestructurally configured as known in the art to access via an Internet 31an exemplary array of servers in the form a web server 41, a file server42, an e-commerce server 43, a content management server 44, a real-timecommunication server 45, a streaming media server 46, a database server47, a mobile information server 48 and a directory server 49, which areoptionally linked via an Intranet 32. In practice, fantasy playerinformation and sponsorship information are managed by this array ofservers 41-49, and fantasy content manager 70 and fantasy gameplaymanager 80 are embodied as software and/or firmwareinstalled/distributed within one or more of the servers 41-49 wherebythe processors of servers 41-49 can execute instructions of the softwareand/or firmware to implement the various inventive principles of thepresent invention.

Those having ordinary skill in the art will appreciate that the array ofservers 41-49 can physically exist as separate hardware platforms orlogically exist on a minimum number of hardware platforms. Those havingordinary skill in the art will appreciate that some of the servers 41-49can be eliminated and/or other types of servers can be added to thisarray. In one embodiment, web server 41 can individually execute theinstructions of fantasy content manager 70 and fantasy gameplay manager80 while fantasy player information and/or sponsorship information canbe managed by file server 42, content management server 44, stream mediaserver 46, and/or database server 47.

Referring to FIGS. 1-14, the present invention does not impose anylimitations or any restrictions to the form of fantasy client requestswhereby any fantasy client request can invoke action by fantasy contentmanager 70 and/or fantasy gameplay manager 80. In practice, a fantasyclient request can take the form of one of the fantasy client requestsdescribed herein, a combination of two or more of the fantasy clientrequests described herein, or any other form not described herein aswould be appreciated by those having ordinary skill in the art.

Furthermore, in some cases, sponsorship information may be notdesignated to one or more of the fantasy players. During these cases,all requests are executed as taught herein and under the inventiveprinciples of the present invention exclusive of any association ofsponsorship information to fantasy player information.

An alert window can be displayed with fantasy point updates on players.The feed item associated with the alert can be accessed to see astreamed video clip of the play. Alerts can also be given to otherplayer performance that are not being played or those on waivers or notdrafted. In a real time substitution version of fantasy sports, forexample football, the user can determine if it would be beneficial toreplace a player that is injured or not performing well. In anotherwindow game information, including game score, time remaining, line up,having involved fantasy players can be displayed for both the usersfantasy team and the users opponents fantasy team. The user can thenhave a continuous update of each game.

A user can view all carries by your running back—all routes by yourreceiver—encourage more involvement and more sponsorship. Real timepoint counts on all players and ability to sub in and out during agame—time periods tracked by system. Ability to see what substitutionsyour opponent has made and you can counter with a move—you are ahead andyour opponent subs in a quarterback—if you have the receiver thatquarterback throws to—you can sub in to lessen the potential impact.

One type of information that may be displayed in the single item windowis information related to fantasy sports. For example, a user mayreceive updates on the statistics of players they have specified, playerinjuries, players not currently held in their league that are havingimpressive statistics, scouting reports for weekly matchups, or thelike.

A user may select that all Fantasy Football players on his team and/oropponents team with yardage, touchdowns and Fantasy points be displayedevery 5 minutes or scrolled through while the user is watching TV or asa message to the users portable communication device on Sundays.Friends' messages related to the football or other game can beprioritized for display when the user is watching TV on game day.

FIG. 15 shows representative feed formatted content 1500. Feed formattedcontent is structured data, such as for example Electronic DataInterchange (EDI), Extensible Markup Language (XML), or a subset of ageneral format such as RSS (Rich Site Summary or Really SimpleSyndication), a hybrid or extension of some such standard, or the like.Feed formatted content 1500 may be accessed through a feed, stored in alocal file, or the like. A feed is the data returned when a request forfeed formatted content is made. Feed formatted content may include afeed header 1501. In one embodiment, feed header 1501 includes a headerlabeling feed formatted content 1500 as XML data, and further providestwo element wrappers: rss and channel. Feed formatted content 1500 oftenrepresents multiple items, as is that displayed in FIG. 1. Each feeditem 1506 may represent one or more news headlines, events, searchresults, items for sale or any other data. Feed item 1506 may containany number of elements. For example, it may include a title element1507, link element 1508, and a description element 1509. The term feedformatted content may describe an entire feed, a portion of a feed, afeed item, or a portion of a feed item.

One type of information that may be displayed in the single item windowis information related to fantasy sports. FIG. 16 illustrates aflowchart representative of one embodiment of a method for providingfeed formatted content at 4000. Fantasy league and team data is storedat 4002. New fantasy information is received at 4004. For example, aserver may receive feed formatted content representing fantasyinformation. A determination is then made whether the received fantasyinformation is related to the league and team date. If the informationis related, feed formatted content is provided at 4406. For example, auser may receive updates on the statistics of players they havespecified, player injuries, players not currently held in their leaguethat are having impressive statistics, scouting reports for weeklymatchups, or the like. In one embodiment, a fantasy sports informationfeed may be provided for each player in a sport. Alternatively, the feedmay include information in feed items indicating what play theinformation may be associated with.

In one embodiment, feed formatted content may facilitate fantasy leagueplay. FIG. 17 illustrates a flowchart representative of one embodimentof a method for operating a real time fantasy sports league at 4100. Auser provides a fantasy team player list at 4102. A server creates feedformatted content based on real time statistics and on the fantasy teamplayer list and provides the feed formatted content to the user at 4104.The user provides a substitution request at 4106. The server receivesthe substitution request, determines a time associated with thesubstitution, and modifies the feed formatted content based on thesubstitution request and the determined time at 4108. For example,statistics and feed formatted content may be provided and tallied to auser based on their specified team. A user may note that a player hasbeen injured, or that it is halftime in a game, and may substitute in analternate player at that time. The provided and tallied statistics mayrepresent the team with the substitute starting at the time thesubstitution is submitted.

In one embodiment, feed items may include one or more video, audio, oraudio/video clips or links to one or more video, audio, or audio/videoclips. Such a feed may be read to a computer, a cellphone, an internetconnected digital video recorder (DVR), or the like. In one embodiment,a DVR or other device may aggregate clips into a highlight reel ofimportant fantasy sports plays, for example for a user's active playersin a league. FIG. 18 illustrates a flowchart representative of oneembodiment of a method for operating a real time fantasy sports leagueat 4200. A user provides a fantasy team player list at 4202. A serverreceives a plurality of fantasy team players, receives a list of videoclips, creates feed formatted content based on the video clips and theplayers, and provides the feed formatted content at 4204. The userprovides a request for a video clip based on the provided feed formattedcontent at 4206. The server may receive the request for a video clip andprovide access to the video clip at 4208. In this way a user may requesteither an individual highlight video clip of a fantasy player, or, inone embodiment, the user may request all video clips associated with oneor more of their players. When more than one video clip is selected, aplaylist may be provided. In one embodiment, the playlist may includeone or more accompanying audio clips, for example selected by the user,to play in conjunction with the playlist. Commentary, audio, video orwritten may also be included in the feed formatted content. For example,an opponent may make supply a heckling comment to accompany a play inwhich one a user's key player is injured.

In one embodiment, a fantasy sports feed can be continuously adjustedbased on user selected or IAP suggested or provided factors, forexample, for fantasy football some factors may include: player versusdefense strength, player versus opponent time of possession, player'shistorical performance against opponent team, players performance atstadium, weather conditions, opponents players, player's recentperformance, injury reports, etc. The user may select factors for theplayer selection feed, which then based on the factors selects the bestteam from the users fantasy team and all other available players. Forexample, during a football season Sunday, a fantasy player may beinjured; the feed will provide a replacement player based on theselected or provided factors. The feed may make the selection for theuser or alert the user with a feed item alert.

Those having ordinary skill in the art will further appreciate variousobjects and advantages of the present invention, such as, for example, arealization of a comprehensive sponsorship of fantasy players on anindividual basis and/or a team basis with an improved exchange offantasy content between fantasy client devices 20 and fantasy serversystem 40.

While the embodiments of the invention disclosed herein are presentlyconsidered to be preferred, various changes and modifications can bemade without departing from the spirit and scope of the presentinvention. The scope of the invention is indicated in the appendedclaims, and all changes that come within the meaning and range ofequivalents are intended to be embraced therein.

We claim:
 1. A fantasy league system comprising: a fantasy serversystem; and a fantasy client device operable to communicate over theInternet with the fantasy server system; wherein the fantasy serversystem is operable to: store fantasy player information regarding one ormore real-world athletes, store sponsorship information associated withthe fantasy player on at least one of an individual basis and a teambasis, receive an operational request from the fantasy client device,said operational request designating an operational aspect, determine anassociation between the operational request and the fantasy player,determine an operational result based on the operational request,associate at least one item of sponsorship information to theoperational result based at least in part upon said sponsorshipinformation associated with the fantasy player, transmit the operationalresult and the at least one associated item of sponsorship informationto the first fantasy client device; and wherein the fantasy clientdevice is operable to: send an operational request, and display an alertwindow including the sponsorship information based on the transmittedoperational result.
 2. The system of claim 1, wherein the operationalaspect is an off-season action.
 3. The system of claim 1, wherein theoperational aspect is an in-season action.
 4. The system of claim 3,wherein the in-season action is a transaction involving the fantasyplayer.
 5. The system of claim 4, wherein the transaction comprisesdrafting the fantasy player.
 6. The system of claim 4, wherein thetransaction comprises acquiring the fantasy player.
 7. The system ofclaim 4, wherein the transaction comprises releasing the fantasy player.8. The system of claim 4, wherein the transaction comprises substitutingthe fantasy player.
 9. The system of claim 1, wherein the alert windowdisplays the sponsorship information prior to displaying the operationalresult.
 10. A computer-implemented method for operating a fantasy leagueusing a fantasy server system operable to communicate over the Internetwith a fantasy client device, the method comprising: storing fantasyplayer information regarding one or more real-world athletes in thefantasy server system; storing sponsorship information associated withthe fantasy player on at least one of an individual basis and a teambasis in the fantasy server system; receiving an operational requestfrom the first fantasy client device at the fantasy server system, saidoperational request designating an operational aspect; determining anassociation between the operational request and the fantasy player;determining an operational result based on the operational request;associating at least one item of sponsorship information with theoperational result based at least in part upon said sponsorshipinformation associated with the fantasy player; transmitting theoperational result and the at least one associated item of sponsorshipinformation from the fantasy server system to the first fantasy clientdevice; and displaying an alert window at the first fantasy clientdevice including the sponsorship information based on the transmittedoperational result.
 11. The method of claim 10, wherein the operationalaspect is an off-season action.
 12. The method of claim 11, wherein theoperational aspect is an in-season action.
 13. The method of claim 12,wherein the in-season action is a transaction involving the fantasyplayer.
 14. The method of claim 13, wherein the transaction comprisesdrafting the fantasy player.
 15. The method of claim 13, wherein thetransaction comprises acquiring the fantasy player.
 16. The method ofclaim 13, wherein the transaction comprises releasing the fantasyplayer.
 17. The method of claim 13, wherein the transaction comprisessubstituting the fantasy player.
 18. The method of claim 10, wherein thealert window displays the sponsorship information prior to displayingthe operational result.
 19. A fantasy league system comprising: afantasy server system; a first fantasy client device in communicationwith the fantasy server system via a network; wherein the fantasy serversystem is operable to: store fantasy player information regarding one ormore real-world athletes, store sponsorship information associated withthe fantasy player on at least one of an individual basis and a teambasis, receive a fantasy player draft request from the first fantasyclient device specifying the fantasy player, determines a draftselection based on the fantasy player draft request, associates thefantasy player with a fantasy team based on the determination, associateat least one item of sponsorship information to the draft selectionbased at least in part upon said sponsorship information associated withthe fantasy player, transmit the draft selection and the at least oneassociated item of sponsorship information to the first fantasy clientdevice; and wherein the first fantasy client device is operable to: senda fantasy player draft request, and display an alert window includingthe sponsorship information based on the transmitted draft selection.20. The system of claim 19, further comprising a second fantasy clientdevice: wherein the fantasy server system is operable to transmit thedraft selection and the at least one item of sponsorship information tothe second fantasy client device; and wherein the second fantasy clientdevice is operable to display an alert window including the sponsorshipinformation based on the draft selection transmitted to the secondfantasy client device.